This whitepaper explores the short-comings of legacy ECM platforms, and how ECMnext vendors can step up and deliver what we’ve wanted out of ECM all along. While there’s still a ways to go for ECMnext platforms to be able to completely replace legacy ECM platforms, the basic building blocks are in place and the roadmaps are pointing in the right direction
As a perfect example of the industry and legacy ECM platforms headed for change, Costco is at the beginning stages of planning for the next generation of Content platforms and solutions
I believe the distinction between ECM and CCM should continue as a way to differentiate between two very different models and modes of working. Legacy ECM software is licensed per seat, by concurrent users or CPU count(s) with associated software maintenance
The “critical” documents are kept in a legacy ECM system and several SharePoint doclibs store the non-critical documents...The business users work primarily with the legacy ECM system, but often also need to work with the documents in SharePoint
SharePoint is competing at one level against the simplicity of storing documents in Box and Dropbox, and at another level against the complexity of building solutions in legacy ECM platforms like Open Text and Documentum
Let’s compare that to a legacy ECM system or SharePoint
1 Comment - no search term matches found in comments.
I’m glad you asked … I attended BoxWorks in September 2014 ( my thoughts , if you’re interested) and I’ve also been pretty interested in the whole not-EFSS space for a while; I’ve concluded that Box and some others are going to supplant the legacy ECM vendors even as ECM transitions to being a collection of functions required to deliver IG
SharePoint's growth is largely based on simple economics -- organizations realized they can sunset legacy ECM apps and save money
As a platform it can be built into many different types of solutions – including many of the core elements of what are common in legacy ECM solutions. SharePoint allows for the Rise of the Experts
The focal point should be: How SharePoint fits into the business objectives of the organization at the enterprise level What organizational structures need to be put in place to define and support the use of SharePoint (e.g. a Governance Committee, User Adoption Strategy, Content Taxonomy) How various SharePoint features can be used and/or combined to replace or complement existing systems and processes (e.g. the Corporate Intranet, Line of Business Applications, legacy ECM solutions) At a minimum, I think Decision Makers need to understand, at a high level , what the following features are and how they might be used to solve common business-technical problems: Various options for implementing Web-based Data Input Forms and Workflows in SharePoint Document Libraries, Document Sets, the Document ID Service and Remote Blob Storage Enterprise Content Types & the Managed Metadata Service Content Organizer, Drop-off Library and Content Organization Rules In-place Records Management in SharePoint 2010 Integration Support including Business Connectivity Services (BCS), the Business Data Catalog, SharePoint Web Services, etc